When a provider properly implements text field controls, setting the value property on the outer text field node is redundant, because the text is already provided in the inner inline text boxes. I expect that this would be a performance problem for large amounts of text. So now, accesskit_consumer provides its own value property for single-line text controls, based on the inner text. For multi-line controls without an outer value property, the macOS adapter fires value change events as appropriate, just as the Windows adapter already fires text change events. I've tested these changes on both Windows and macOS using a modified version of egui that doesn't set the value property on the text field.